Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Upgrade Swagger 2.2.15 -> 2.2.16 #795

Merged
merged 1 commit into from
Oct 4, 2023
Merged

Upgrade Swagger 2.2.15 -> 2.2.16 #795

merged 1 commit into from
Oct 4, 2023

Conversation

Picnic-Bot
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
Swagger compile patch 2.2.15 -> 2.2.16

Release Notes

swagger-api/swagger-core (Swagger)

v2.2.16: Swagger-core 2.2.16 released!

Compare Source

  • downgrade GH release actions runs-on (#​4477)
  • fix python setup in release GH Action (#​4476)
  • refs #​3080 - support array in additionalProperties annotation member (#​4475)
  • allow null values for extensions properties in openapi object (#​4468)
  • fixes #​4458 - correct invocation of setSkipResolveAppPath (#​4459)
  • add support of visibility of properties not annotated with jsonview b… (#​4391)
  • If you want to rebase/retry this PR, check this box

@Picnic-Bot
Copy link
Contributor Author

Picnic-Bot commented Sep 19, 2023 •
edited by Stephan202
Loading

Suggested commit message:

Upgrade Swagger 2.2.15 -> 2.2.16 (#795)

See:
- https://github.com/swagger-api/swagger-core/releases/tag/v2.2.16
- https://github.com/swagger-api/swagger-core/compare/v2.2.15...v2.2.16

@Stephan202 Stephan202 added this to the 0.14.0 milestone Sep 19, 2023
@Picnic-Bot Picnic-Bot force-pushed the renovate/swagger-2.x branch from 055c525 to 0ce9a71 Compare October 3, 2023 01:29
@rickie rickie force-pushed the renovate/swagger-2.x branch from 0ce9a71 to bb647ee Compare October 3, 2023 14:09
@github-actions
Copy link

github-actions bot commented Oct 3, 2023

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

@rickie
Copy link
Member

rickie commented Oct 3, 2023

@Stephan202 You probably forgot to press approve 😉.

1 similar comment
@rickie
Copy link
Member

rickie commented Oct 3, 2023

@Stephan202 You probably forgot to press approve 😉.

Stephan202
Stephan202 approved these changes Oct 3, 2023
View reviewed changes
Copy link
Member

@Stephan202 Stephan202 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Uh-oh!

@Picnic-Bot Picnic-Bot force-pushed the renovate/swagger-2.x branch from bb647ee to 03432cd Compare October 4, 2023 01:06
@rickie rickie force-pushed the renovate/swagger-2.x branch from 03432cd to f26f09e Compare October 4, 2023 06:37
@sonarqubecloud
Copy link

sonarqubecloud bot commented Oct 4, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@github-actions
Copy link

github-actions bot commented Oct 4, 2023

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

@rickie rickie merged commit 7d912d1 into master Oct 4, 2023
17 checks passed
@rickie rickie deleted the renovate/swagger-2.x branch October 4, 2023 06:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@rickie rickie rickie approved these changes

@Stephan202 Stephan202 Stephan202 approved these changes

Assignees
No one assigned
Labels
dependencies
Milestone
0.14.0
Development

Successfully merging this pull request may close these issues.
3 participants
@Picnic-Bot @rickie @Stephan202